Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50bd8e166e590d6a3ebcd1a273a24580df302a46a56f76e66712bce4337160ef

Tx prefix hash: f656d2385d6409ddbc7c59b7e27f207a7b2ca6738da83e62bd04e40ebe67d8f0
Tx public key: 1b049e3812d13d458c3d45e9381b52ca2cf60daf8e1f529c5f5d36411bc64298
Timestamp: 1701299205 Timestamp [UCT]: 2023-11-29 23:06:45 Age [y:d:h:m:s]: 00:351:04:25:56
Block: 902507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251468 RingCT/type: yes/0
Extra: 011b049e3812d13d458c3d45e9381b52ca2cf60daf8e1f529c5f5d36411bc6429802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.627508539000 dcy

stealth address amount amount idx
00: 0935801b93f4ab85d2ea0b7973ed41cc5192291c7222fb2edc61a22beb3ed195 0.627508539000 1359150 of 0

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": 902517, "vin": [ { "gen": { "height": 902507 } } ], "vout": [ { "amount": 627508539, "target": { "key": "0935801b93f4ab85d2ea0b7973ed41cc5192291c7222fb2edc61a22beb3ed195" } } ], "extra": [ 1, 27, 4, 158, 56, 18, 209, 61, 69, 140, 61, 69, 233, 56, 27, 82, 202, 44, 246, 13, 175, 142, 31, 82, 156, 95, 93, 54, 65, 27, 198, 66, 152, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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