Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44defcd9122fcb15098db135c0041265ec9dea3d8744e78c911cec28eb3d775d

Tx prefix hash: 722d681c34774ef2a1dbcc66aaa0c2f1cb0c84d5fd41275cbdf2cac268015552
Tx public key: b9ba55af1f3f0bb49b99e7eea2f5baedb9f0afed4547822a9f1292cd80b482bc
Timestamp: 1729586896 Timestamp [UCT]: 2024-10-22 08:48:16 Age [y:d:h:m:s]: 00:142:19:33:28
Block: 1137002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101878 RingCT/type: yes/0
Extra: 01b9ba55af1f3f0bb49b99e7eea2f5baedb9f0afed4547822a9f1292cd80b482bc02110000000120d1394b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e93e9e5875f7e1766c9cee84b990725e6ad835e72ffa64d47ae479e04d00afa 0.600000000000 1620411 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": 1137012, "vin": [ { "gen": { "height": 1137002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e93e9e5875f7e1766c9cee84b990725e6ad835e72ffa64d47ae479e04d00afa" } } ], "extra": [ 1, 185, 186, 85, 175, 31, 63, 11, 180, 155, 153, 231, 238, 162, 245, 186, 237, 185, 240, 175, 237, 69, 71, 130, 42, 159, 18, 146, 205, 128, 180, 130, 188, 2, 17, 0, 0, 0, 1, 32, 209, 57, 75, 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