Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26972a0c7984a2fff6088b0ec830872ed11ba718c93f35433209c40e40e639bb

Tx prefix hash: 89ef727a54ae5e5174cb20aa19411302364f73f0118d5eb043b10ea068a64f63
Tx public key: 47aee89c66e2d0e0f181f600cfc9fbbc12370b3c22d584081ce05c36be66e1ae
Timestamp: 1733644499 Timestamp [UCT]: 2024-12-08 07:54:59 Age [y:d:h:m:s]: 00:120:07:16:41
Block: 1170579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85771 RingCT/type: yes/0
Extra: 0147aee89c66e2d0e0f181f600cfc9fbbc12370b3c22d584081ce05c36be66e1ae02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 993a74e012ee24028e3202d2fcc3308d66e1cb3219841c360722c5c3123cff68 0.600000000000 1656310 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": 1170589, "vin": [ { "gen": { "height": 1170579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "993a74e012ee24028e3202d2fcc3308d66e1cb3219841c360722c5c3123cff68" } } ], "extra": [ 1, 71, 174, 232, 156, 102, 226, 208, 224, 241, 129, 246, 0, 207, 201, 251, 188, 18, 55, 11, 60, 34, 213, 132, 8, 28, 224, 92, 54, 190, 102, 225, 174, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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