Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8bbebcd28020d0ef5537983e2f66a862812c13cc7d7ba8fe5258efb484207bd

Tx prefix hash: a67bb608a71f213ce31c574d569fe1e08dfd64c3cc30972d99ae1097f9acd01a
Tx public key: 29ad1144e1728ffc45e5c221d93be84af891e2cb00f2ab0181b40d0e0979f6c0
Timestamp: 1730468250 Timestamp [UCT]: 2024-11-01 13:37:30 Age [y:d:h:m:s]: 00:151:19:21:47
Block: 1144259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108321 RingCT/type: yes/0
Extra: 0129ad1144e1728ffc45e5c221d93be84af891e2cb00f2ab0181b40d0e0979f6c0021100000003007f978a000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: c1d67fb5503c67dd95cdc1696dd3edabbda6ee8f507b7ad3508732a60490d732 0.608000000000 1628414 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": 1144269, "vin": [ { "gen": { "height": 1144259 } } ], "vout": [ { "amount": 608000000, "target": { "key": "c1d67fb5503c67dd95cdc1696dd3edabbda6ee8f507b7ad3508732a60490d732" } } ], "extra": [ 1, 41, 173, 17, 68, 225, 114, 143, 252, 69, 229, 194, 33, 217, 59, 232, 74, 248, 145, 226, 203, 0, 242, 171, 1, 129, 180, 13, 14, 9, 121, 246, 192, 2, 17, 0, 0, 0, 3, 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