Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc37b55b174d8d7ea2995e040c8af162bc2c172efb5fdde8d37b2d14a17e908

Tx prefix hash: 227c65bcc04cadb5c41a2026a1bfdcfd86bd04e431603632a1ba38512a617c2b
Tx public key: 148ec04a62a0f80810e05e751a3e919f87873b2449bb1f26da0856edf1c64e7d
Timestamp: 1713894770 Timestamp [UCT]: 2024-04-23 17:52:50 Age [y:d:h:m:s]: 01:247:03:31:21
Block: 1006941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435344 RingCT/type: yes/0
Extra: 01148ec04a62a0f80810e05e751a3e919f87873b2449bb1f26da0856edf1c64e7d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac7d59911ad2028776e33315d7b379287cbed7816316f451df2ea9a94321733 0.600000000000 1468131 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": 1006951, "vin": [ { "gen": { "height": 1006941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac7d59911ad2028776e33315d7b379287cbed7816316f451df2ea9a94321733" } } ], "extra": [ 1, 20, 142, 192, 74, 98, 160, 248, 8, 16, 224, 94, 117, 26, 62, 145, 159, 135, 135, 59, 36, 73, 187, 31, 38, 218, 8, 86, 237, 241, 198, 78, 125, 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