Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b2040ca48c80a6f4b9e48dd14d439f4df0c1c3b3aa9c88ce54dbf2eb4c84d08

Tx prefix hash: f2f9f7544fc42bb30a8b4b49eea6eab49d8fa37a6c1a43c31eaa94d34e65bcdf
Tx public key: 2d2e8ff9ae7b90ef9b4503e52cdda02fa008e98f0832bc284d096fbd62184bd6
Timestamp: 1663626150 Timestamp [UCT]: 2022-09-19 22:22:30 Age [y:d:h:m:s]: 02:147:03:35:55
Block: 591546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626514 RingCT/type: yes/0
Extra: 012d2e8ff9ae7b90ef9b4503e52cdda02fa008e98f0832bc284d096fbd62184bd602110000000533af99f4000000000000000000

1 output(s) for total of 6.729187225000 dcy

stealth address amount amount idx
00: 4ec413e29551f9c85a7af7560bfba2ed950a02060474ded5358338349538a0a3 6.729187225000 1026091 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": 591556, "vin": [ { "gen": { "height": 591546 } } ], "vout": [ { "amount": 6729187225, "target": { "key": "4ec413e29551f9c85a7af7560bfba2ed950a02060474ded5358338349538a0a3" } } ], "extra": [ 1, 45, 46, 143, 249, 174, 123, 144, 239, 155, 69, 3, 229, 44, 221, 160, 47, 160, 8, 233, 143, 8, 50, 188, 40, 77, 9, 111, 189, 98, 24, 75, 214, 2, 17, 0, 0, 0, 5, 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