Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fb3b4e8f3b962a326146147a4c77dafcf7d9c2bf59fd6705d4fc9445ecb5e4

Tx prefix hash: f274b248612e61775c8469f01e17b316f32c281afe6d491e25ef5dabb4ea8b7c
Tx public key: 150a0a0dc6be86b5dc414db78ed50234ae14d45a50f446bd5257a54914d79131
Timestamp: 1713396701 Timestamp [UCT]: 2024-04-17 23:31:41 Age [y:d:h:m:s]: 00:314:00:43:56
Block: 1002793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224488 RingCT/type: yes/0
Extra: 01150a0a0dc6be86b5dc414db78ed50234ae14d45a50f446bd5257a54914d7913102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b771d54a355678f047bc6f5b569d42046e285ce687b80751965e801f6094c67a 0.600000000000 1463317 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": 1002803, "vin": [ { "gen": { "height": 1002793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b771d54a355678f047bc6f5b569d42046e285ce687b80751965e801f6094c67a" } } ], "extra": [ 1, 21, 10, 10, 13, 198, 190, 134, 181, 220, 65, 77, 183, 142, 213, 2, 52, 174, 20, 212, 90, 80, 244, 70, 189, 82, 87, 165, 73, 20, 215, 145, 49, 2, 17, 0, 0, 0, 5, 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