Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ba77f420babcfd203bb8e20f15fa77af71177ee803073e04c5517015a8f7f8b

Tx prefix hash: 8432bace22983466dade900823bb3f85ad0dd7403a62dd7e33c6b4f5b8f21d1b
Tx public key: 1bb8e810e0a9dcfef57d07603f520f1690e46694edac5c3c5fe54d48f992e2ed
Timestamp: 1707640262 Timestamp [UCT]: 2024-02-11 08:31:02 Age [y:d:h:m:s]: 00:277:08:07:37
Block: 955078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198584 RingCT/type: yes/0
Extra: 011bb8e810e0a9dcfef57d07603f520f1690e46694edac5c3c5fe54d48f992e2ed02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0d79ec296b05db2f2e4af48cb1799978bb30c643c9118be2f5a1ea5a1366a6 0.600000000000 1414360 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": 955088, "vin": [ { "gen": { "height": 955078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0d79ec296b05db2f2e4af48cb1799978bb30c643c9118be2f5a1ea5a1366a6" } } ], "extra": [ 1, 27, 184, 232, 16, 224, 169, 220, 254, 245, 125, 7, 96, 63, 82, 15, 22, 144, 228, 102, 148, 237, 172, 92, 60, 95, 229, 77, 72, 249, 146, 226, 237, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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