Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7da7e95914fe38340d1335918f415c662a03c138fca607829ccf80bd1b458dcb

Tx prefix hash: ae47c5c2ea7f0f3c63691dfdefaaaea0feee3875c6ae7bfe262f35b3a1cc45c4
Tx public key: 595cf7128b2dd58d18a8c8c097130a5761494c6913f932b3311093f14ce28079
Timestamp: 1713868720 Timestamp [UCT]: 2024-04-23 10:38:40 Age [y:d:h:m:s]: 00:204:00:40:47
Block: 1006725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146053 RingCT/type: yes/0
Extra: 01595cf7128b2dd58d18a8c8c097130a5761494c6913f932b3311093f14ce280790211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 571c50ce7803ce4ed367b85e0396dc8f3f94de626775a69a3f6736df6dffc959 0.600000000000 1467843 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": 1006735, "vin": [ { "gen": { "height": 1006725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "571c50ce7803ce4ed367b85e0396dc8f3f94de626775a69a3f6736df6dffc959" } } ], "extra": [ 1, 89, 92, 247, 18, 139, 45, 213, 141, 24, 168, 200, 192, 151, 19, 10, 87, 97, 73, 76, 105, 19, 249, 50, 179, 49, 16, 147, 241, 76, 226, 128, 121, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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