Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b51943c6f09f0ba6e6ec80bf29cd89adde4ee37d7ba7bc1a0722c0e40153198

Tx prefix hash: d13c5bda222b7cfb3a8086472b00a00b990a3ce55e8e7ed7a018792572921a90
Tx public key: a9219eff5ca4277ae8d777f2a441d8d8b4176fb675fd2761a07bd881b339e13f
Timestamp: 1705079679 Timestamp [UCT]: 2024-01-12 17:14:39 Age [y:d:h:m:s]: 01:299:00:04:37
Block: 933836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472504 RingCT/type: yes/0
Extra: 01a9219eff5ca4277ae8d777f2a441d8d8b4176fb675fd2761a07bd881b339e13f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f6dbdb3c563f371c84b4b471ce0a83d6cb9e174898d31fa713bb21810797333 0.600000000000 1391820 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": 933846, "vin": [ { "gen": { "height": 933836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6dbdb3c563f371c84b4b471ce0a83d6cb9e174898d31fa713bb21810797333" } } ], "extra": [ 1, 169, 33, 158, 255, 92, 164, 39, 122, 232, 215, 119, 242, 164, 65, 216, 216, 180, 23, 111, 182, 117, 253, 39, 97, 160, 123, 216, 129, 179, 57, 225, 63, 2, 17, 0, 0, 0, 2, 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