Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d11fd768aaba0c8d178eff0019b0349e4f0ce2e2bf26605058dc3655c1903de5

Tx prefix hash: 5c341f83028ca242c17564ed555cefe0fd76bdc905829af2a731d770c19a8da5
Tx public key: 807a0857582e59de7290a610bc779fa719cc277cd3e58ec60a817fd31856b118
Timestamp: 1749714897 Timestamp [UCT]: 2025-06-12 07:54:57 Age [y:d:h:m:s]: 00:162:08:00:41
Block: 1303316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113727 RingCT/type: yes/0
Extra: 01807a0857582e59de7290a610bc779fa719cc277cd3e58ec60a817fd31856b118021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd1e52c93e86a2172f136eb57523d9d3e094d78a3cafdf72d21a7d532deb7902 0.600000000000 1790895 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": 1303326, "vin": [ { "gen": { "height": 1303316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1e52c93e86a2172f136eb57523d9d3e094d78a3cafdf72d21a7d532deb7902" } } ], "extra": [ 1, 128, 122, 8, 87, 88, 46, 89, 222, 114, 144, 166, 16, 188, 119, 159, 167, 25, 204, 39, 124, 211, 229, 142, 198, 10, 129, 127, 211, 24, 86, 177, 24, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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