Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f53f2cc456ad412ba3cbcb00f67ca28208de97619c99d66a43f792a6e4e2de

Tx prefix hash: af52a8279d00753e01eef5412c0b5ff71576a5413e57760710bc40697b64c798
Tx public key: 2e489b1d5b9beb69396ac5e9d2d27dc196b3cf833ec4a774478db6a7f96e122e
Timestamp: 1684156346 Timestamp [UCT]: 2023-05-15 13:12:26 Age [y:d:h:m:s]: 01:320:18:58:19
Block: 760645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490486 RingCT/type: yes/0
Extra: 012e489b1d5b9beb69396ac5e9d2d27dc196b3cf833ec4a774478db6a7f96e122e02110000000433af99f4000000000000000000

1 output(s) for total of 1.852113272000 dcy

stealth address amount amount idx
00: 4b3f3b8f2b5ad7d9b309c5463abe6a9911b23fd42e008c4f912b825c6548e246 1.852113272000 1209274 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": 760655, "vin": [ { "gen": { "height": 760645 } } ], "vout": [ { "amount": 1852113272, "target": { "key": "4b3f3b8f2b5ad7d9b309c5463abe6a9911b23fd42e008c4f912b825c6548e246" } } ], "extra": [ 1, 46, 72, 155, 29, 91, 155, 235, 105, 57, 106, 197, 233, 210, 210, 125, 193, 150, 179, 207, 131, 62, 196, 167, 116, 71, 141, 182, 167, 249, 110, 18, 46, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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