Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb2ff4f2b03c3b54f94afc2d6902414aec81b02f148a9c46d9aa9b677039692

Tx prefix hash: 778c7eb5fb46d05a77e712dfba29702b7c68456de6765dfa6d000f86637f4de1
Tx public key: dd7c4571b378fd2a201f10185bdb6f5f4ae25d38eb63f855c442209c141a798d
Timestamp: 1673811629 Timestamp [UCT]: 2023-01-15 19:40:29 Age [y:d:h:m:s]: 02:040:06:37:41
Block: 675492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550420 RingCT/type: yes/0
Extra: 01dd7c4571b378fd2a201f10185bdb6f5f4ae25d38eb63f855c442209c141a798d021100000004044c7254000000000000000000

1 output(s) for total of 3.546619055000 dcy

stealth address amount amount idx
00: 35e04ced7adc3281df9ddaa7d3a48fcbc3d002f7420de6215d72051a7dc04ce2 3.546619055000 1117171 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": 675502, "vin": [ { "gen": { "height": 675492 } } ], "vout": [ { "amount": 3546619055, "target": { "key": "35e04ced7adc3281df9ddaa7d3a48fcbc3d002f7420de6215d72051a7dc04ce2" } } ], "extra": [ 1, 221, 124, 69, 113, 179, 120, 253, 42, 32, 31, 16, 24, 91, 219, 111, 95, 74, 226, 93, 56, 235, 99, 248, 85, 196, 66, 32, 156, 20, 26, 121, 141, 2, 17, 0, 0, 0, 4, 4, 76, 114, 84, 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