Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3d4a2a918f53bd3e8a7027416daa0b4fe0fbcc5c5493115d270a798ebdcffe

Tx prefix hash: cfc93783e91a78dfecf7b95bb9bcf6241666748764ed54c33a0ccb4f43a762b1
Tx public key: 671b1a3f3eaf3c297bfef95aa99cfa8cdd22d71749bb55d011313952ccaa32d5
Timestamp: 1716195987 Timestamp [UCT]: 2024-05-20 09:06:27 Age [y:d:h:m:s]: 01:027:13:22:56
Block: 1026020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280518 RingCT/type: yes/0
Extra: 01671b1a3f3eaf3c297bfef95aa99cfa8cdd22d71749bb55d011313952ccaa32d50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74e5ae1291dccae2a7b7101cf9aed9d3ffd7e4fedfc7e6d5941ade17a474f5cb 0.600000000000 1492873 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": 1026030, "vin": [ { "gen": { "height": 1026020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74e5ae1291dccae2a7b7101cf9aed9d3ffd7e4fedfc7e6d5941ade17a474f5cb" } } ], "extra": [ 1, 103, 27, 26, 63, 62, 175, 60, 41, 123, 254, 249, 90, 169, 156, 250, 140, 221, 34, 215, 23, 73, 187, 85, 208, 17, 49, 57, 82, 204, 170, 50, 213, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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