Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1d3c7979dc294a528d2875fe93f833bbd3c901b1913d231ffa2c1e695d3c77

Tx prefix hash: 89cde35d1db417d7babe8780595a8bd0c426d2367758a75828763f2e123d6407
Tx public key: 49aff0c5102b4e2c4dbc7e1d925d4cdec04761188c993fc9708c29d676e0fb1e
Timestamp: 1672470826 Timestamp [UCT]: 2022-12-31 07:13:46 Age [y:d:h:m:s]: 02:097:17:30:02
Block: 664370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591538 RingCT/type: yes/0
Extra: 0149aff0c5102b4e2c4dbc7e1d925d4cdec04761188c993fc9708c29d676e0fb1e021100000002faf35c9c000000000000000000

1 output(s) for total of 3.860702727000 dcy

stealth address amount amount idx
00: b2c63b0b96dee863a289d52e9149ee01cbc57f5fcec42a7589dc2b59a319e9b8 3.860702727000 1105345 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": 664380, "vin": [ { "gen": { "height": 664370 } } ], "vout": [ { "amount": 3860702727, "target": { "key": "b2c63b0b96dee863a289d52e9149ee01cbc57f5fcec42a7589dc2b59a319e9b8" } } ], "extra": [ 1, 73, 175, 240, 197, 16, 43, 78, 44, 77, 188, 126, 29, 146, 93, 76, 222, 192, 71, 97, 24, 140, 153, 63, 201, 112, 140, 41, 214, 118, 224, 251, 30, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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