Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993cd6217c4c064fc0d56bf53324fa5c59ff133865a7689b32de5fc3745f8f02

Tx prefix hash: b45ba3ef236bc964caf71493805e203fe6b6bff2f55b77596ba1024d9b5279c3
Tx public key: 5e392e799f1d7be553db5dddc3f0c77081bd89e2038d8c80efa7a07c431ea5fd
Timestamp: 1673109063 Timestamp [UCT]: 2023-01-07 16:31:03 Age [y:d:h:m:s]: 01:317:21:02:07
Block: 669660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488184 RingCT/type: yes/0
Extra: 015e392e799f1d7be553db5dddc3f0c77081bd89e2038d8c80efa7a07c431ea5fd02110000000352542ceb000000000000000000

1 output(s) for total of 3.707988586000 dcy

stealth address amount amount idx
00: 4166a8dc32a799675bc2ead8ba101a7874e5ef3f382199929ac31ed288d85f49 3.707988586000 1111011 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": 669670, "vin": [ { "gen": { "height": 669660 } } ], "vout": [ { "amount": 3707988586, "target": { "key": "4166a8dc32a799675bc2ead8ba101a7874e5ef3f382199929ac31ed288d85f49" } } ], "extra": [ 1, 94, 57, 46, 121, 159, 29, 123, 229, 83, 219, 93, 221, 195, 240, 199, 112, 129, 189, 137, 226, 3, 141, 140, 128, 239, 167, 160, 124, 67, 30, 165, 253, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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