Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2743da48ee81c29f33d0e4bc63d48ef0fd0c829f86633dd0722c5a43cdd806

Tx prefix hash: edb051749725663bbd2a3f0849072c839d9a0af3153ce95834b96e8d3a0aa1a2
Tx public key: afbc873d747bcdc36d2e6be98ba183707273a51fc6294ed8397abf864ec70d38
Timestamp: 1694369269 Timestamp [UCT]: 2023-09-10 18:07:49 Age [y:d:h:m:s]: 01:172:14:45:51
Block: 845242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384452 RingCT/type: yes/0
Extra: 01afbc873d747bcdc36d2e6be98ba183707273a51fc6294ed8397abf864ec70d380211000000014b8f5122000000000000000000

1 output(s) for total of 0.971320246000 dcy

stealth address amount amount idx
00: 64cb56d7b3c852bfe20efab74caa2bdc3657f9b75195192d4bb7f1b48c76c0ee 0.971320246000 1298606 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": 845252, "vin": [ { "gen": { "height": 845242 } } ], "vout": [ { "amount": 971320246, "target": { "key": "64cb56d7b3c852bfe20efab74caa2bdc3657f9b75195192d4bb7f1b48c76c0ee" } } ], "extra": [ 1, 175, 188, 135, 61, 116, 123, 205, 195, 109, 46, 107, 233, 139, 161, 131, 112, 114, 115, 165, 31, 198, 41, 78, 216, 57, 122, 191, 134, 78, 199, 13, 56, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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