Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d354fdaaf6f3b3eee51926469f4dde6c117e307b17a920b51ebcadaedd8d28

Tx prefix hash: bf580c187aaba7d01986b7cad8df9facb0a514e16a24c4f73f4ceb43f77b81dd
Tx public key: 3f477bdf8f743dc038a93a54e6a58bb66b666de7b61fc41c7540ce093a1d86d3
Timestamp: 1705303124 Timestamp [UCT]: 2024-01-15 07:18:44 Age [y:d:h:m:s]: 01:059:17:19:46
Block: 935690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303793 RingCT/type: yes/0
Extra: 013f477bdf8f743dc038a93a54e6a58bb66b666de7b61fc41c7540ce093a1d86d30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd651113264521ad3c1ce001417f7933efa23030c875e24eed1731c4bb40c71c 0.600000000000 1393706 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": 935700, "vin": [ { "gen": { "height": 935690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd651113264521ad3c1ce001417f7933efa23030c875e24eed1731c4bb40c71c" } } ], "extra": [ 1, 63, 71, 123, 223, 143, 116, 61, 192, 56, 169, 58, 84, 230, 165, 139, 182, 107, 102, 109, 231, 182, 31, 196, 28, 117, 64, 206, 9, 58, 29, 134, 211, 2, 17, 0, 0, 0, 1, 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