Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad70e76b33eaaab1013e0d53aaf03e62ce06fd1c27dc06deeab2416eacff8d7e

Tx prefix hash: 386d78ca10b16df180b29dbb1f01ff2e4dcc1241b7c57e4aad022649535ea0f3
Tx public key: 9f784442e294940e6ebcd7ebaa569beaf9e66193c5b168599c216eaf4ac50a02
Timestamp: 1745751810 Timestamp [UCT]: 2025-04-27 11:03:30 Age [y:d:h:m:s]: 00:011:19:54:50
Block: 1270540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8447 RingCT/type: yes/0
Extra: 019f784442e294940e6ebcd7ebaa569beaf9e66193c5b168599c216eaf4ac50a020211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c786b5a05f889dd7a711aa3b57775cf928f14235f03a28d9328c78e462f01d 0.600000000000 1757783 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": 1270550, "vin": [ { "gen": { "height": 1270540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c786b5a05f889dd7a711aa3b57775cf928f14235f03a28d9328c78e462f01d" } } ], "extra": [ 1, 159, 120, 68, 66, 226, 148, 148, 14, 110, 188, 215, 235, 170, 86, 155, 234, 249, 230, 97, 147, 197, 177, 104, 89, 156, 33, 110, 175, 74, 197, 10, 2, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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