Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb47cb5f9a4d031a41cea892e24d523037b9fd52a896e089dee8aa658488b0e9

Tx prefix hash: 48691b86730687f7af9137d48e45c80be78636ff05a038f28001bb60a4cf00c2
Tx public key: 9169e817cd68082610971e9e81c4d77797f03aa8582f9296f1e72cb24a4da713
Timestamp: 1631624592 Timestamp [UCT]: 2021-09-14 13:03:12 Age [y:d:h:m:s]: 03:242:02:26:26
Block: 333641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 948466 RingCT/type: yes/0
Extra: 019169e817cd68082610971e9e81c4d77797f03aa8582f9296f1e72cb24a4da71302110000003836fe6557000000000000000000

1 output(s) for total of 48.140357071000 dcy

stealth address amount amount idx
00: 39387e644cf3f57a556413aac5ee5951707d3512cc3bfa0be12de1fdda3a7b13 48.140357071000 688404 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": 333651, "vin": [ { "gen": { "height": 333641 } } ], "vout": [ { "amount": 48140357071, "target": { "key": "39387e644cf3f57a556413aac5ee5951707d3512cc3bfa0be12de1fdda3a7b13" } } ], "extra": [ 1, 145, 105, 232, 23, 205, 104, 8, 38, 16, 151, 30, 158, 129, 196, 215, 119, 151, 240, 58, 168, 88, 47, 146, 150, 241, 231, 44, 178, 74, 77, 167, 19, 2, 17, 0, 0, 0, 56, 54, 254, 101, 87, 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