Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b27cbfbcad11c57a70d9ca79004c9277157bae62ffb9553c0b5d1fc84bcf51

Tx prefix hash: d365d6012b15c16407ec458d5da9dc50acb95f3b1e41d36a3cdb52c32e832f28
Tx public key: f143a6c63aa93c09f6d94d1480e25a97c9c9d569285e860b89eb20c64171aeb1
Timestamp: 1735669506 Timestamp [UCT]: 2024-12-31 18:25:06 Age [y:d:h:m:s]: 00:304:03:21:33
Block: 1187328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214876 RingCT/type: yes/0
Extra: 01f143a6c63aa93c09f6d94d1480e25a97c9c9d569285e860b89eb20c64171aeb1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f0ffa9db3d51abe718b4cab5ee991fe3901481e1edd0ecd099761445260f64 0.600000000000 1673817 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": 1187338, "vin": [ { "gen": { "height": 1187328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f0ffa9db3d51abe718b4cab5ee991fe3901481e1edd0ecd099761445260f64" } } ], "extra": [ 1, 241, 67, 166, 198, 58, 169, 60, 9, 246, 217, 77, 20, 128, 226, 90, 151, 201, 201, 213, 105, 40, 94, 134, 11, 137, 235, 32, 198, 65, 113, 174, 177, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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