Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a47e6007464ae581b52d7f2c974b8509b0223e5ebde610390f7ade62c6b754

Tx prefix hash: 11e9b7cfd19af3d07db8c80b5d391912bcfebc1b0cfdeaa7d7068d3c97a72019
Tx public key: 3d412850e3d80764a21cedbe3a6e1a11ed4501a0d8257292d07eb70d2ad37629
Timestamp: 1719636739 Timestamp [UCT]: 2024-06-29 04:52:19 Age [y:d:h:m:s]: 01:127:05:40:40
Block: 1054541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349465 RingCT/type: yes/0
Extra: 013d412850e3d80764a21cedbe3a6e1a11ed4501a0d8257292d07eb70d2ad3762902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83b5546439ae2aa2a9ec46038865f6bf4eb16723a3d09bc4ac0bad2294d4d0f5 0.600000000000 1524904 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": 1054551, "vin": [ { "gen": { "height": 1054541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83b5546439ae2aa2a9ec46038865f6bf4eb16723a3d09bc4ac0bad2294d4d0f5" } } ], "extra": [ 1, 61, 65, 40, 80, 227, 216, 7, 100, 162, 28, 237, 190, 58, 110, 26, 17, 237, 69, 1, 160, 216, 37, 114, 146, 208, 126, 183, 13, 42, 211, 118, 41, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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