Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b38fb34b4eef9901ba3922430a91641aaa339552d0a468bac67b25400833f8a

Tx prefix hash: 8a606aacf65a3f7e84f0f8160b68883b82b3249064f4285de491648734a4f6f6
Tx public key: 009aae2b0c3bb151ce2ded895861c4210f0cb3e5814fe365e17e186700d54cc3
Timestamp: 1695511702 Timestamp [UCT]: 2023-09-23 23:28:22 Age [y:d:h:m:s]: 01:207:15:19:08
Block: 854737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409478 RingCT/type: yes/0
Extra: 01009aae2b0c3bb151ce2ded895861c4210f0cb3e5814fe365e17e186700d54cc3021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.903444650000 dcy

stealth address amount amount idx
00: f04e3429cd2b8882b16b5f4d2e63d7f07509c11eadda71ebb254223e0de88275 0.903444650000 1308723 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": 854747, "vin": [ { "gen": { "height": 854737 } } ], "vout": [ { "amount": 903444650, "target": { "key": "f04e3429cd2b8882b16b5f4d2e63d7f07509c11eadda71ebb254223e0de88275" } } ], "extra": [ 1, 0, 154, 174, 43, 12, 59, 177, 81, 206, 45, 237, 137, 88, 97, 196, 33, 15, 12, 179, 229, 129, 79, 227, 101, 225, 126, 24, 103, 0, 213, 76, 195, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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