Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfd85af1826b9ff130b1ebf88385cc8bdb031290061225fdc61321740b9de72

Tx prefix hash: f16deca654b5312ca5b924e2958ff27fcd2a7fbdfc6007e252e648fb370f9aa7
Tx public key: d3bd63676a6f5ee9184af79d5bd37d447f2c8850bf44725c574ee3ea58209f2c
Timestamp: 1685378549 Timestamp [UCT]: 2023-05-29 16:42:29 Age [y:d:h:m:s]: 02:164:03:35:20
Block: 770784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637091 RingCT/type: yes/0
Extra: 01d3bd63676a6f5ee9184af79d5bd37d447f2c8850bf44725c574ee3ea58209f2c02110000000233af99f4000000000000000000

1 output(s) for total of 1.714244691000 dcy

stealth address amount amount idx
00: d85d8d2f260eaa083bc1b5b43682ac835cac2001b6d7ccf4b63e5aca22e5eb43 1.714244691000 1220115 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": 770794, "vin": [ { "gen": { "height": 770784 } } ], "vout": [ { "amount": 1714244691, "target": { "key": "d85d8d2f260eaa083bc1b5b43682ac835cac2001b6d7ccf4b63e5aca22e5eb43" } } ], "extra": [ 1, 211, 189, 99, 103, 106, 111, 94, 233, 24, 74, 247, 157, 91, 211, 125, 68, 127, 44, 136, 80, 191, 68, 114, 92, 87, 78, 227, 234, 88, 32, 159, 44, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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