Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2844549468ae541d084f6aae9c33f45e5969ecf25801b54d19db6c55e3414f9

Tx prefix hash: d17f033140f0d6c7d5c0c90c1badaae16047a1cfcc54865a62c6b930fa04de6b
Tx public key: fedc303f21716488331289d48af0ffd42acb8cfe50117f04ff94e21c85ea3964
Timestamp: 1709470727 Timestamp [UCT]: 2024-03-03 12:58:47 Age [y:d:h:m:s]: 01:036:20:36:46
Block: 970276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287336 RingCT/type: yes/0
Extra: 01fedc303f21716488331289d48af0ffd42acb8cfe50117f04ff94e21c85ea396402110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 332117a03838ea4e15c876db8b8b4a6806d9eb3a58e189bd33d49e5820684b1e 0.600000000000 1430127 of 15

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": 970286, "vin": [ { "gen": { "height": 970276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "332117a03838ea4e15c876db8b8b4a6806d9eb3a58e189bd33d49e5820684b1e" } } ], "extra": [ 1, 254, 220, 48, 63, 33, 113, 100, 136, 51, 18, 137, 212, 138, 240, 255, 212, 42, 203, 140, 254, 80, 17, 127, 4, 255, 148, 226, 28, 133, 234, 57, 100, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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