Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec55aa80f0636301bb01b1f13f1872b0240243fc326a07d71ee4834ae422422d

Tx prefix hash: b93c578c268cc002eacac313a72e29f937d026c9e857fdf5aa68742e439846d0
Tx public key: f51e53f5bb45b15892aee63902f0d7e90bd7b65845dcf8a0f8d634c51b872349
Timestamp: 1672615536 Timestamp [UCT]: 2023-01-01 23:25:36 Age [y:d:h:m:s]: 01:336:20:28:20
Block: 665574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501774 RingCT/type: yes/0
Extra: 01f51e53f5bb45b15892aee63902f0d7e90bd7b65845dcf8a0f8d634c51b87234902110000000475e3f0e9000000000000000000

1 output(s) for total of 3.825401368000 dcy

stealth address amount amount idx
00: 7d05ceb654991273a6c1e68b9d5cd5c3bd3d490ba26b8cb0452eacdf92e920c1 3.825401368000 1106623 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": 665584, "vin": [ { "gen": { "height": 665574 } } ], "vout": [ { "amount": 3825401368, "target": { "key": "7d05ceb654991273a6c1e68b9d5cd5c3bd3d490ba26b8cb0452eacdf92e920c1" } } ], "extra": [ 1, 245, 30, 83, 245, 187, 69, 177, 88, 146, 174, 230, 57, 2, 240, 215, 233, 11, 215, 182, 88, 69, 220, 248, 160, 248, 214, 52, 197, 27, 135, 35, 73, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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