Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c27c1814159b10644723fab8d2fa473d8153c609556286b41c2e415979f54fc2

Tx prefix hash: 2a3585f1fa50d978e49db7d56fac97784a1ac629704ab05f9f8322d14892226c
Tx public key: 045e35e44f51aae9350b98cc1a28b6062b088788a02497e5f3cb90afdf0cc95f
Timestamp: 1702670553 Timestamp [UCT]: 2023-12-15 20:02:33 Age [y:d:h:m:s]: 01:354:19:03:53
Block: 913879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512481 RingCT/type: yes/0
Extra: 01045e35e44f51aae9350b98cc1a28b6062b088788a02497e5f3cb90afdf0cc95f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9afaa1e03699f744f56dee500412cd23d4aae00dc7241f4ef27aae39bc889af0 0.600000000000 1371159 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 913889, "vin": [ { "gen": { "height": 913879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9afaa1e03699f744f56dee500412cd23d4aae00dc7241f4ef27aae39bc889af0" } } ], "extra": [ 1, 4, 94, 53, 228, 79, 81, 170, 233, 53, 11, 152, 204, 26, 40, 182, 6, 43, 8, 135, 136, 160, 36, 151, 229, 243, 203, 144, 175, 223, 12, 201, 95, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8