Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1522f30ca56878ec38c4652aac468b6e7ec62f96d3c13f17a5a00fc95343be1

Tx prefix hash: 8da0931eae7a5c0df74f6be92e74b9a7f335b8ad81945fd5598cfc84b5af46fb
Tx public key: 367b0fb7944eca95970046801c9ce5466a5d1980ed4f8d1728b00fe3ba98dfd1
Timestamp: 1737545755 Timestamp [UCT]: 2025-01-22 11:35:55 Age [y:d:h:m:s]: 00:051:04:17:37
Block: 1202822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36408 RingCT/type: yes/0
Extra: 01367b0fb7944eca95970046801c9ce5466a5d1980ed4f8d1728b00fe3ba98dfd1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3189123ced7e11d7a41d038bf3a079a4f71c58b03df2f463978c65a25e1148e 0.600000000000 1689489 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": 1202832, "vin": [ { "gen": { "height": 1202822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3189123ced7e11d7a41d038bf3a079a4f71c58b03df2f463978c65a25e1148e" } } ], "extra": [ 1, 54, 123, 15, 183, 148, 78, 202, 149, 151, 0, 70, 128, 28, 156, 229, 70, 106, 93, 25, 128, 237, 79, 141, 23, 40, 176, 15, 227, 186, 152, 223, 209, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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