Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2be50c0f352a0da844182cf80f05bf178b2da96178610095e08031b122a7d1

Tx prefix hash: b0c35e2727926918d3f1a47a52cb1060b8379e95b972cb5d1278c26de9bab8ff
Tx public key: fefd8cf898a9abdb0a015ebd184680d9138327dc90bedd521d4a0e3633812e60
Timestamp: 1635051453 Timestamp [UCT]: 2021-10-24 04:57:33 Age [y:d:h:m:s]: 03:026:04:52:20
Block: 359296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797014 RingCT/type: yes/0
Extra: 01fefd8cf898a9abdb0a015ebd184680d9138327dc90bedd521d4a0e3633812e600211000000193fc41461000000000000000000

1 output(s) for total of 39.583875606000 dcy

stealth address amount amount idx
00: 9462404fac3903bb8d359843df1951f2c7be643e03b1ae89892c601f882e1025 39.583875606000 731727 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": 359306, "vin": [ { "gen": { "height": 359296 } } ], "vout": [ { "amount": 39583875606, "target": { "key": "9462404fac3903bb8d359843df1951f2c7be643e03b1ae89892c601f882e1025" } } ], "extra": [ 1, 254, 253, 140, 248, 152, 169, 171, 219, 10, 1, 94, 189, 24, 70, 128, 217, 19, 131, 39, 220, 144, 190, 221, 82, 29, 74, 14, 54, 51, 129, 46, 96, 2, 17, 0, 0, 0, 25, 63, 196, 20, 97, 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