Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27fd921513d4d80b5b19284345bbb999235d8d0e879d59fbe97644466d87dfa9

Tx prefix hash: b3d30db4fd4f4cb0cccda9e4c85780d06c74f24009fe0afc9fb17db2c2f5f99a
Tx public key: fee73e7ca422ca2a32b431d93b01c5294ae7c19ff54896069bd12a70c5da14e7
Timestamp: 1728348427 Timestamp [UCT]: 2024-10-08 00:47:07 Age [y:d:h:m:s]: 00:253:00:22:45
Block: 1126772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180543 RingCT/type: yes/0
Extra: 01fee73e7ca422ca2a32b431d93b01c5294ae7c19ff54896069bd12a70c5da14e702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d56ab4fa23be49c57d8c41c0a95547c72256e77e05a4cd70e86d41844e17f3e 0.600000000000 1609567 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": 1126782, "vin": [ { "gen": { "height": 1126772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d56ab4fa23be49c57d8c41c0a95547c72256e77e05a4cd70e86d41844e17f3e" } } ], "extra": [ 1, 254, 231, 62, 124, 164, 34, 202, 42, 50, 180, 49, 217, 59, 1, 197, 41, 74, 231, 193, 159, 245, 72, 150, 6, 155, 209, 42, 112, 197, 218, 20, 231, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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