Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504dd91be4ec3ca405cdda0b7b43aa9f12cc947ff846c82037c59d887960cda7

Tx prefix hash: b11650f190bfe23982655c5f4a5779de170c5578aa83eac6e847a950ec4c74ed
Tx public key: 435dd2d61e462310fd44d7eb2e1e51258ea3dbafa81eececafec041bf61e2a1b
Timestamp: 1682592766 Timestamp [UCT]: 2023-04-27 10:52:46 Age [y:d:h:m:s]: 02:165:14:42:32
Block: 747680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638163 RingCT/type: yes/0
Extra: 01435dd2d61e462310fd44d7eb2e1e51258ea3dbafa81eececafec041bf61e2a1b021100000003b3164c24000000000000000000

1 output(s) for total of 2.044683017000 dcy

stealth address amount amount idx
00: 0e0e68260f7d2c980ce332d6c1c67ed9af7ea9a77f2ee87653640edf04153dd2 2.044683017000 1195407 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": 747690, "vin": [ { "gen": { "height": 747680 } } ], "vout": [ { "amount": 2044683017, "target": { "key": "0e0e68260f7d2c980ce332d6c1c67ed9af7ea9a77f2ee87653640edf04153dd2" } } ], "extra": [ 1, 67, 93, 210, 214, 30, 70, 35, 16, 253, 68, 215, 235, 46, 30, 81, 37, 142, 163, 219, 175, 168, 30, 236, 236, 175, 236, 4, 27, 246, 30, 42, 27, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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