Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28e9602d7a9adfaa01012cfbdb1e769e8ff8264c7c4762b0a6b50d595c5d6d0

Tx prefix hash: 970886b257e44ad074a45ec09d4138660ec09a1b413b9bbf92eca9a2b7aeaf5e
Tx public key: b2fbc5e6ba9448f89d9d2d7014134af7a1d8df46ec297e432ba6dffd91804607
Timestamp: 1736050881 Timestamp [UCT]: 2025-01-05 04:21:21 Age [y:d:h:m:s]: 00:090:15:22:33
Block: 1190501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64550 RingCT/type: yes/0
Extra: 01b2fbc5e6ba9448f89d9d2d7014134af7a1d8df46ec297e432ba6dffd91804607021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7867cb3f1b3c00577bc4f026f9a6f7b873c50fa79f388ad76711a11fc114c9f 0.600000000000 1677018 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": 1190511, "vin": [ { "gen": { "height": 1190501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7867cb3f1b3c00577bc4f026f9a6f7b873c50fa79f388ad76711a11fc114c9f" } } ], "extra": [ 1, 178, 251, 197, 230, 186, 148, 72, 248, 157, 157, 45, 112, 20, 19, 74, 247, 161, 216, 223, 70, 236, 41, 126, 67, 43, 166, 223, 253, 145, 128, 70, 7, 2, 17, 0, 0, 0, 5, 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